SherbyNet - /page/wikibook/entry.mu

Micron Document

<!DOCTYPE html>

<title>Spanning Tree Protocol</title>

</head>

Spanning Tree Protocol

</h1>

</header>

/* start https://en.wikipedia.org/ */

.mw-parser-output .hlist dl,.mw-parser-output .hlist ol,.mw-parser-output .hlist ul{margin:0;padding:0}.mw-parser-output .hlist dd,.mw-parser-output .hlist dt,.mw-parser-output .hlist li{margin:0;display:inline}.mw-parser-output .hlist.inline,.mw-parser-output .hlist.inline dl,.mw-parser-output .hlist.inline ol,.mw-parser-output .hlist.inline ul,.mw-parser-output .hlist dl dl,.mw-parser-output .hlist dl ol,.mw-parser-output .hlist dl ul,.mw-parser-output .hlist ol dl,.mw-parser-output .hlist ol ol,.mw-parser-output .hlist ol ul,.mw-parser-output .hlist ul dl,.mw-parser-output .hlist ul ol,.mw-parser-output .hlist ul ul{display:inline}.mw-parser-output .hlist .mw-empty-li{display:none}.mw-parser-output .hlist dt::after{content:": "}.mw-parser-output .hlist dd::after,.mw-parser-output .hlist li::after{content:" · ";font-weight:bold}.mw-parser-output .hlist dd:last-child::after,.mw-parser-output .hlist dt:last-child::after,.mw-parser-output .hlist li:last-child::after{content:none}.mw-parser-output .hlist dd dd:first-child::before,.mw-parser-output .hlist dd dt:first-child::before,.mw-parser-output .hlist dd li:first-child::before,.mw-parser-output .hlist dt dd:first-child::before,.mw-parser-output .hlist dt dt:first-child::before,.mw-parser-output .hlist dt li:first-child::before,.mw-parser-output .hlist li dd:first-child::before,.mw-parser-output .hlist li dt:first-child::before,.mw-parser-output .hlist li li:first-child::before{content:" (";font-weight:normal}.mw-parser-output .hlist dd dd:last-child::after,.mw-parser-output .hlist dd dt:last-child::after,.mw-parser-output .hlist dd li:last-child::after,.mw-parser-output .hlist dt dd:last-child::after,.mw-parser-output .hlist dt dt:last-child::after,.mw-parser-output .hlist dt li:last-child::after,.mw-parser-output .hlist li dd:last-child::after,.mw-parser-output .hlist li dt:last-child::after,.mw-parser-output .hlist li li:last-child::after{content:")";font-weight:normal}.mw-parser-output .hlist ol{counter-reset:listitem}.mw-parser-output .hlist ol>li{counter-increment:listitem}.mw-parser-output .hlist ol>li::before{content:" "counter(listitem)"\a0 "}.mw-parser-output .hlist dd ol>li:first-child::before,.mw-parser-output .hlist dt ol>li:first-child::before,.mw-parser-output .hlist li ol>li:first-child::before{content:" ("counter(listitem)"\a0 "}

/* end https://en.wikipedia.org/ */

</style><style data-mw-deduplicate="TemplateStyles:r1246091330">

/* start https://en.wikipedia.org/ */

.mw-parser-output .sidebar{width:22em;float:right;clear:right;margin:0.5em 0 1em 1em;background:var(--background-color-neutral-subtle,#f8f9fa);border:1px solid var(--border-color-base,#a2a9b1);padding:0.2em;text-align:center;line-height:1.4em;font-size:88%;border-collapse:collapse;display:table}body.skin-minerva .mw-parser-output .sidebar{display:table!important;float:right!important;margin:0.5em 0 1em 1em!important}.mw-parser-output .sidebar-subgroup{width:100%;margin:0;border-spacing:0}.mw-parser-output .sidebar-left{float:left;clear:left;margin:0.5em 1em 1em 0}.mw-parser-output .sidebar-none{float:none;clear:both;margin:0.5em 1em 1em 0}.mw-parser-output .sidebar-outer-title{padding:0 0.4em 0.2em;font-size:125%;line-height:1.2em;font-weight:bold}.mw-parser-output .sidebar-top-image{padding:0.4em}.mw-parser-output .sidebar-top-caption,.mw-parser-output .sidebar-pretitle-with-top-image,.mw-parser-output .sidebar-caption{padding:0.2em 0.4em 0;line-height:1.2em}.mw-parser-output .sidebar-pretitle{padding:0.4em 0.4em 0;line-height:1.2em}.mw-parser-output .sidebar-title,.mw-parser-output .sidebar-title-with-pretitle{padding:0.2em 0.8em;font-size:145%;line-height:1.2em}.mw-parser-output .sidebar-title-with-pretitle{padding:0.1em 0.4em}.mw-parser-output .sidebar-image{padding:0.2em 0.4em 0.4em}.mw-parser-output .sidebar-heading{padding:0.1em 0.4em}.mw-parser-output .sidebar-content{padding:0 0.5em 0.4em}.mw-parser-output .sidebar-content-with-subgroup{padding:0.1em 0.4em 0.2em}.mw-parser-output .sidebar-above,.mw-parser-output .sidebar-below{padding:0.3em 0.8em;font-weight:bold}.mw-parser-output .sidebar-collapse .sidebar-above,.mw-parser-output .sidebar-collapse .sidebar-below{border-top:1px solid #aaa;border-bottom:1px solid #aaa}.mw-parser-output .sidebar-navbar{text-align:right;font-size:115%;padding:0 0.4em 0.4em}.mw-parser-output .sidebar-list-title{padding:0 0.4em;text-align:left;font-weight:bold;line-height:1.6em;font-size:105%}.mw-parser-output .sidebar-list-title-c{padding:0 0.4em;text-align:center;margin:0 3.3em}@media(max-width:640px){body.mediawiki .mw-parser-output .sidebar{width:100%!important;clear:both;float:none!important;margin-left:0!important;margin-right:0!important}}body.skin--responsive .mw-parser-output .sidebar a>img{max-width:none!important}@media screen{html.skin-theme-clientpref-night .mw-parser-output .sidebar:not(.notheme) .sidebar-list-title,html.skin-theme-clientpref-night .mw-parser-output .sidebar:not(.notheme) .sidebar-title-with-pretitle{background:transparent!important}html.skin-theme-clientpref-night .mw-parser-output .sidebar:not(.notheme) .sidebar-title-with-pretitle a{color:var(--color-progressive)!important}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .sidebar:not(.notheme) .sidebar-list-title,html.skin-theme-clientpref-os .mw-parser-output .sidebar:not(.notheme) .sidebar-title-with-pretitle{background:transparent!important}html.skin-theme-clientpref-os .mw-parser-output .sidebar:not(.notheme) .sidebar-title-with-pretitle a{color:var(--color-progressive)!important}}@media print{body.ns-0 .mw-parser-output .sidebar{display:none!important}}

/* end https://en.wikipedia.org/ */

</style><table class="sidebar nomobile nowraplinks hlist"><tbody><tr><th class="sidebar-title"><a href="Internet_protocol_suite" title="Internet protocol suite">Internet protocol suite</a></th></tr><tr><th class="sidebar-heading">

<a href="Application_layer" title="Application layer">Application layer</a></th></tr><tr><td class="sidebar-content">

<li><a href="HTTPS" title="HTTPS">HTTPS</a></li>

<li><a href="Telnet" title="Telnet">Telnet</a></li>

</tr><tr><th class="sidebar-heading">

<a href="Transport_layer" title="Transport layer">Transport layer</a></th></tr><tr><td class="sidebar-content">

</tr><tr><th class="sidebar-heading">

<a href="Internet_layer" title="Internet layer">Internet layer</a></th></tr><tr><td class="sidebar-content">

<li><a href="IPsec" title="IPsec">IPsec</a></li>

</tr><tr><th class="sidebar-heading">

<a href="Link_layer" title="Link layer">Link layer</a></th></tr><tr><td class="sidebar-content">

<li><a href="Tunneling_protocol" title="Tunneling protocol">Tunnels</a></li>

</tr><tr><td class="sidebar-navbar"><style data-mw-deduplicate="TemplateStyles:r1239400231">

/* start https://en.wikipedia.org/ */

.mw-parser-output .navbar{display:inline;font-size:88%;font-weight:normal}.mw-parser-output .navbar-collapse{float:left;text-align:left}.mw-parser-output .navbar-boxtext{word-spacing:0}.mw-parser-output .navbar ul{display:inline-block;white-space:nowrap;line-height:inherit}.mw-parser-output .navbar-brackets::before{margin-right:-0.125em;content:"[ "}.mw-parser-output .navbar-brackets::after{margin-left:-0.125em;content:" ]"}.mw-parser-output .navbar li{word-spacing:-0.125em}.mw-parser-output .navbar a>span,.mw-parser-output .navbar a>abbr{text-decoration:inherit}.mw-parser-output .navbar-mini abbr{font-variant:small-caps;border-bottom:none;text-decoration:none;cursor:inherit}.mw-parser-output .navbar-ct-full{font-size:114%;margin:0 7em}.mw-parser-output .navbar-ct-mini{font-size:114%;margin:0 4em}html.skin-theme-clientpref-night .mw-parser-output .navbar li a abbr{color:var(--color-base)!important}@media(prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .navbar li a abbr{color:var(--color-base)!important}}@media print{.mw-parser-output .navbar{display:none!important}}

/* end https://en.wikipedia.org/ */

</style></td></tr></tbody></table>

The Spanning Tree Protocol (STP) is a <a href="Network_protocol" class="mw-redirect" title="Network protocol">network protocol</a> that builds a loop-free <a href="Logical_topology" class="mw-redirect" title="Logical topology">logical topology</a> for <a href="Ethernet_network" class="mw-redirect" title="Ethernet network">Ethernet networks</a>. The basic function of STP is to prevent <a href="Bridge_loop" class="mw-redirect" title="Bridge loop">bridge loops</a> and the <a href="Broadcast_radiation" class="mw-redirect" title="Broadcast radiation">broadcast radiation</a> that results from them. Spanning tree also allows a <a href="Network_design" class="mw-redirect" title="Network design">network design</a> to include backup links providing <a href="Fault_tolerance" title="Fault tolerance">fault tolerance</a> if an active link fails.

As the name suggests, STP creates a <a href="Spanning_tree" title="Spanning tree">spanning tree</a> that characterizes the relationship of nodes within a network of connected layer-2 <a href="Network_bridge" title="Network bridge">bridges</a>, and disables those links that are not part of the spanning tree, leaving a single active path between any two network nodes. STP is based on an algorithm that was invented by <a href="Radia_Perlman" title="Radia Perlman">Radia Perlman</a> while she was working for <a href="Digital_Equipment_Corporation" title="Digital Equipment Corporation">Digital Equipment Corporation</a>.<a href="#cite_note-perlman_paper-1">[1]</a><a href="#cite_note-2">[2]</a>

In 2001, the <a href="IEEE" class="mw-redirect" title="IEEE">IEEE</a> introduced Rapid Spanning Tree Protocol (RSTP) as 802.1w. RSTP provides significantly faster recovery in response to network changes or failures, introducing new convergence behaviors and bridge port roles to do this. RSTP was designed to be backwards-compatible with standard STP.

STP was originally standardized as <a href="IEEE_802.1D" title="IEEE 802.1D">IEEE 802.1D</a> but the functionality of spanning tree (802.1D), rapid spanning tree (802.1w), and <a href="Multiple_Spanning_Tree_Protocol" title="Multiple Spanning Tree Protocol">Multiple Spanning Tree Protocol</a> (802.1s) has since been incorporated into <a href="IEEE_802.1Q-2014" class="mw-redirect" title="IEEE 802.1Q-2014">IEEE 802.1Q-2014</a>.<a href="#cite_note-802.1Q-3">[3]</a>

While STP is still in use today, in most modern networks its primary use is as a loop-protection mechanism rather than a fault tolerance mechanism. <a href="Link_aggregation" title="Link aggregation">Link aggregation</a> protocols such as <a href="Link_aggregation#Link_Aggregation_Control_Protocol" title="Link aggregation">LACP</a> will bond two or more links to provide fault tolerance while simultaneously increasing overall link capacity.

<div class="mw-heading mw-heading2"><h2 id="Protocol_operation">Protocol operation</h2></div>

/* start https://en.wikipedia.org/ */

.mw-parser-output .tmulti .multiimageinner{display:flex;flex-direction:column}.mw-parser-output .tmulti .trow{display:flex;flex-direction:row;clear:left;flex-wrap:wrap;width:100%;box-sizing:border-box}.mw-parser-output .tmulti .tsingle{margin:1px;float:left}.mw-parser-output .tmulti .theader{clear:both;font-weight:bold;text-align:center;align-self:center;background-color:transparent;width:100%}.mw-parser-output .tmulti .thumbcaption{background-color:transparent}.mw-parser-output .tmulti .text-align-left{text-align:left}.mw-parser-output .tmulti .text-align-right{text-align:right}.mw-parser-output .tmulti .text-align-center{text-align:center}@media all and (max-width:720px){.mw-parser-output .tmulti .thumbinner{width:100%!important;box-sizing:border-box;max-width:none!important;align-items:center}.mw-parser-output .tmulti .trow{justify-content:center}.mw-parser-output .tmulti .tsingle{float:none!important;max-width:100%!important;box-sizing:border-box;text-align:center}.mw-parser-output .tmulti .tsingle .thumbcaption{text-align:left}.mw-parser-output .tmulti .trow>.thumbcaption{text-align:center}}@media screen{html.skin-theme-clientpref-night .mw-parser-output .tmulti .multiimageinner span:not(.skin-invert-image):not(.skin-invert):not(.bg-transparent) img{background-color:white}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .tmulti .multiimageinner span:not(.skin-invert-image):not(.skin-invert):not(.bg-transparent) img{background-color:white}}

/* end https://en.wikipedia.org/ */

</style><div class="thumb tmulti tright"><div class="thumbinner multiimageinner" style="width:608px;max-width:608px"><div class="trow"><div class="tsingle" style="width:302px;max-width:302px"><div class="thumbimage"></div><div class="thumbcaption"><a href="Network_bridge" title="Network bridge">Bridges</a> with Spanning Tree Protocol implementation in a local area network (LAN). One bridge is the STP root bridge. All bridge ports that connect a link between two bridges are either a root port (RP), a designated port (DP), or a blocked port (BP).</div></div><div class="tsingle" style="width:302px;max-width:302px"><div class="thumbimage"></div><div class="thumbcaption">After link failure the spanning tree algorithm computes and spans new least-cost tree.</div></div></div></div></div>

The need for the Spanning Tree Protocol (STP) arose because <a href="Network_switch" title="Network switch">switches</a> in <a href="Local_area_networks" class="mw-redirect" title="Local area networks">local area networks</a> (LANs) are often interconnected using redundant links to improve resilience should one connection fail.<a href="#cite_note-Angelescu-4">[4]</a>: 386 However, this connection configuration creates a <a href="Switching_loop" title="Switching loop">switching loop</a> resulting in <a href="Broadcast_radiation" class="mw-redirect" title="Broadcast radiation">broadcast radiations</a> and <a href="MAC_table" class="mw-redirect" title="MAC table">MAC table</a> instability.<a href="#cite_note-Angelescu-4">[4]</a>: 388 If redundant links are used to connect switches, then switching loops need to be avoided.<a href="#cite_note-Angelescu-4">[4]</a>: 385

To avoid the problems associated with redundant links in a switched LAN, STP is implemented on switches to monitor the network topology. Every link between switches, and in particular redundant links, are catalogued. The spanning-tree algorithm then blocks forwarding on redundant links by setting up one preferred link between switches in the LAN. This preferred link is used for all Ethernet frames unless it fails, in which case a non-preferred redundant link is enabled. When implemented in a network, STP designates one layer-2 switch as root bridge. All switches then select their best connection towards the root bridge for forwarding and block other redundant links. All switches constantly communicate with their neighbors in the LAN using <a href="#Bridge_protocol_data_units">§ Bridge protocol data units</a> (BPDUs).<a href="#cite_note-Angelescu-4">[4]</a>: 388

Provided there is more than one link between two switches, the STP root bridge calculates the cost of each path based on bandwidth. STP will select the path with the lowest cost, that is the highest bandwidth, as the preferred link. STP will enable this preferred link as the only path to be used for Ethernet frames between the two switches, and disable all other possible links by designating the switch ports that connect the preferred path as root port.<a href="#cite_note-Angelescu-4">[4]</a>: 393

After STP enabled switches in a LAN have elected the root bridge, all non-root bridges assign one of their ports as root port. This is either the port that connects the switch to the root bridge, or if there are several paths, the port with the preferred path as calculated by the root bridge. Because not all switches are directly connected to the root bridge they communicate amongst each other using STP BPDUs. Each switch adds the cost of its own path to the cost received from the neighboring switches to determine the total cost of a given path to the root bridge. Once the cost of all possible paths to the root bridge have been added up, each switch assigns a port as root port which connects to the path with the lowest cost, or highest bandwidth, that will eventually lead to the root bridge.<a href="#cite_note-Angelescu-4">[4]</a>: 394

<caption>Path cost for different port speed and STP variation

</caption>

<th>Data rate (link bandwidth)

</th>

<th>Original STP cost (802.1D-1998)

</th>

<th>RSTP/MSTP cost (recommended value)<a href="#cite_note-802.1Q-3">[3]</a>: 503

</th></tr>

<tr>

<td>4 Mbit/s

</td>

<td>250

</td>

<td>5,000,000

</td></tr>

<tr>

<td>10 Mbit/s

</td>

<td>100

</td>

<td>2,000,000

</td></tr>

<tr>

<td>16 Mbit/s

</td>

<td>62

</td>

<td>1,250,000

</td></tr>

<tr>

<td>100 Mbit/s

</td>

<td>19

</td>

<td>200,000

</td></tr>

<tr>

<td>1 Gbit/s

</td>

<td>4

</td>

<td>20,000

</td></tr>

<tr>

<td>2 Gbit/s

</td>

<td>3

</td>

<td>10,000

</td></tr>

<tr>

<td>10 Gbit/s

</td>

<td>2

</td>

<td>2,000

</td></tr>

<tr>

<td>100 Gbit/s

</td>

<td>N/A

</td>

<td>200

</td></tr>

<tr>

<td>1 Tbit/s

</td>

<td>N/A

</td>

<td>20

</td></tr></tbody></table>

The STP path cost default was originally calculated by the formula <style data-mw-deduplicate="TemplateStyles:r1214402035">

/* start https://en.wikipedia.org/ */

.mw-parser-output .sfrac{white-space:nowrap}.mw-parser-output .sfrac.tion,.mw-parser-output .sfrac .tion{display:inline-block;vertical-align:-0.5em;font-size:85%;text-align:center}.mw-parser-output .sfrac .num{display:block;line-height:1em;margin:0.0em 0.1em;border-bottom:1px solid}.mw-parser-output .sfrac .den{display:block;line-height:1em;margin:0.1em 0.1em}.mw-parser-output .sr-only{border:0;clip:rect(0,0,0,0);clip-path:polygon(0px 0px,0px 0px,0px 0px);height:1px;margin:-1px;overflow:hidden;padding:0;position:absolute;width:1px}

/* end https://en.wikipedia.org/ */

</style>⁠1 Gbit/s/bandwidth⁠. When faster speeds became available, the default values were adjusted as otherwise speeds above 1 Gbit/s would have been indistinguishable by STP. Its successor RSTP uses a similar formula with a larger numerator: ⁠20 Tbit/s/bandwidth⁠. These formulas lead to the sample values in the table.<a href="#cite_note-802.1D-2004-5">[5]</a>: 154

<div class="mw-heading mw-heading3"><h3 id="Port_states">Port states</h3></div>

All switch ports in the LAN where STP is enabled are categorized.<a href="#cite_note-Angelescu-4">[4]</a>: 388

<dl><dt>Blocking</dt>

<dd>A port that would cause a switching loop if it were active. To prevent the use of looped paths, no user data is sent or received over a blocking port. BPDU data is still received in blocking state. A blocked port may go into forwarding mode if the other links in use fail and the spanning tree algorithm determines the port may transition to the forwarding state.</dd>

<dt>Listening</dt>

<dd>The switch processes BPDUs and awaits possible new information that would cause it to return to the blocking state. It does not populate the <a href="MAC_table" class="mw-redirect" title="MAC table">MAC table</a> and it does not forward frames.</dd>

<dt>Learning</dt>

<dd>While the port does not yet forward frames, it does learn source addresses from frames received and adds them to the MAC table.</dd>

<dt>Forwarding</dt>

<dd>A port in normal operation receiving and forwarding frames. The port monitors incoming BPDUs that would indicate it should return to the blocking state to prevent a loop.</dd>

<dt>Disabled</dt>

<dd>A network administrator has manually disabled the switch port.</dd></dl>

When a device is first attached to a switch port, it will not immediately start to forward data. It will instead go through a number of states while it processes BPDUs and determines the topology of the network. The port attached to a host such as a computer, printer or <a href="Server_(computing)" title="Server (computing)">server</a> always goes into the forwarding state, albeit after a delay of about 30 seconds while it goes through the listening and learning states. The time spent in the listening and learning states is determined by a value known as the forward delay (default 15 seconds and set by the root bridge). If another switch is connected, the port may remain in blocking mode if it is determined that it would cause a loop in the network. Topology change notification (TCN) BPDUs are used to inform other switches of port changes. TCNs are injected into the network by a non-root switch and propagated to the root. Upon receipt of the TCN, the root switch will set the topology change flag in its normal BPDUs. This flag is propagated to all other switches and instructs them to rapidly age out their forwarding table entries.

<div class="mw-heading mw-heading2"><h2 id="Configuration">Configuration</h2></div>

Before configuring STP, the network topology should be carefully planned.<a href="#cite_note-CCNPCSG-6">[6]</a>: 506, 511 Basic configuration requires that STP be enabled on all switches in the LAN and the same version of STP chosen on each. The administrator may determine which switch will be the root bridge and configure the switches appropriately. If the root bridge goes down, the protocol will automatically assign a new root bridge based on bridge ID. If all switches have the same bridge ID, such as the default ID, and the root bridge goes down, a tie situation arises and the protocol will assign one switch as root bridge based on the switch MAC addresses. Once the switches have been assigned a bridge ID and the protocol has chosen the root bridge switch, the best path to the root bridge is calculated based on port cost, path cost and port priority.<a href="#cite_note-CCNPCSG-6">[6]</a>: 506 Ultimately STP calculates the path cost on the basis of the bandwidth of a link, however links between switches may have the same bandwidth. Administrators can influence the protocol's choice of the preferred path by configuring the port cost; the lower the port cost the more likely it is that the protocol will choose the connected link as root port for the preferred path.<a href="#cite_note-CCNPCSG-6">[6]</a>: 511 The selection of how other switches in the topology choose their root port, or the least cost path to the root bridge, can be influenced by the port priority. The highest priority will mean the path will ultimately be less preferred. If all ports of a switch have the same priority, the port with the lowest number is chosen to forward frames.<a href="#cite_note-CCNPCSG-6">[6]</a>: 513

<div class="mw-heading mw-heading3"><h3 id="Root_bridge_and_the_bridge_ID">Root bridge and the bridge ID</h3></div>

The root bridge of the spanning tree is the bridge with the smallest (lowest) bridge ID. Each bridge has a configurable priority number and a MAC address; the bridge ID is the <a href="Concatenation" title="Concatenation">concatenation</a> of the bridge priority and the MAC address. For example, the ID of a bridge with priority 32,768 and MAC 0200.0000.1111 is 32768.0200.0000.1111. The bridge priority default is 32,768 and can be configured only in multiples of 4096.<a href="#cite_note-7">[a]</a> When comparing two bridge IDs, the priority portions are compared first and the MAC addresses are compared only if the priorities are equal. The switch with the lowest priority of all the switches will be the root; if there is a tie, then the switch with the lowest priority and lowest MAC address will be the root. For example, if switches A (MAC = 0200.0000.1111) and B (MAC = 0200.0000.2222) both have a priority of 32,768 then switch A will be selected as the root bridge.<a href="#cite_note-8">[b]</a> If the network administrators would like switch B to become the root bridge, they must set its priority to be less than 32,768.<a href="#cite_note-10">[c]</a>

<div class="mw-heading mw-heading3"><h3 id="Path_to_the_root_bridge">Path to the root bridge</h3></div>

The sequence of events to determine the best received BPDU (which is the best path to the root) is:

<ol><li>Lowest root bridge ID (BID) – Determines the root bridge.</li>

<li>Lowest cost to the root bridge – Favors the upstream switch with the least cost to root</li>

<li>Lowest sender bridge ID – Serves as a tiebreaker if multiple upstream switches have equal cost to root</li>

<li>Lowest sender port ID – Serves as a tiebreaker if a switch has multiple (non-<a href="EtherChannel" title="EtherChannel">EtherChannel</a>) links to a single upstream switch, where:

<ul><li>Bridge ID = priority (4 bits) + locally assigned system ID extension (12 bits) + ID [MAC address] (48 bits); the default bridge priority is 32,768, and</li>

<li>Port ID = priority (4 bits) + ID (Interface number) (12 bits); the default port priority is 128.</li></ul></li></ol>

<div class="mw-heading mw-heading3"><h3 id="Tiebreakers">Tiebreakers</h3></div>

<dl><dt>Root ports</dt>

<dd>When multiple paths from a bridge are least-cost paths, the chosen path uses the neighbor bridge with the lower bridge ID. The root port is thus the one connecting to the bridge with the lowest bridge ID. For example, in the figures, if switch 4 were connected to <a href="Network_segment" title="Network segment">network segment</a> d instead of segment f, there would be two paths of length 2 to the root, one path going through bridge 24 and the other through bridge 92. Because there are two least-cost paths, the lower bridge ID (24) would be used as the tiebreaker in choosing which path to use.</dd>

<dt>Paths</dt>

<dd>When more than one bridge on a segment leads to a least-cost path to the root, the bridge with the lower bridge ID is used to forward messages to the root. The port attaching that bridge to the network segment is the designated port for the segment. In the figures, there are two least-cost paths from network segment d to the root, one going through bridge 24 and the other through bridge 92. The lower bridge ID is 24, so the tiebreaker dictates that the designated port is the port through which network segment d is connected to bridge 24. If bridge IDs were equal, then the bridge with the lowest MAC address would have the designated port. In either case, the loser sets the port as being blocked.</dd>

<dt>Designated ports</dt>

<dd>When the root bridge has more than one port on a single network segment, the bridge ID is effectively tied, as are all root path costs (all equal zero). The port on that network segment with the lowest port ID becomes the designated port. It is put into forwarding mode while all other ports on the root bridge on that same network segment become non-designated ports and are put into blocking mode.<a href="#cite_note-11">[8]</a> Not all bridge manufacturers follow this rule, instead making all root bridge ports designated ports, and putting them all in forwarding mode.</dd>

<dt>Final tiebreaker</dt>

<dd>In some cases, there may still be a tie, as when the root bridge has multiple active ports on the same network segment (see above) with equally low root path costs and bridge IDs, or, in other cases, multiple bridges are connected by multiple cables and multiple ports. In each case, a single bridge may have multiple candidates for its root port. In these cases, candidates for the root port have already received BPDUs offering equally-low (i.e. the "best") root path costs and equally-low (i.e. the "best") bridge IDs, and the final tiebreaker goes to the port that received the lowest (i.e. the "best") port priority ID, or port ID.<a href="#cite_note-12">[9]</a></dd></dl>

<div class="mw-heading mw-heading2"><h2 id="Bridge_protocol_data_units">Bridge protocol data units</h2></div>

The above rules describe one way of determining what spanning tree will be computed by the algorithm, but the rules as written require knowledge of the entire network. The <a href="Network_bridge" title="Network bridge">bridges</a> have to determine the root bridge and compute the port roles (root, designated, or blocked) with only the information that they have. To ensure that each bridge has enough information, the bridges use special data <a href="Frame_(networking)" title="Frame (networking)">frames</a> called bridge protocol data units (BPDUs) to exchange information about the Spanning Tree Protocol, bridge IDs, and root path costs.

<caption>Example <a href="IEEE_802.3" title="IEEE 802.3">802.3 Ethernet</a> frame<a href="#cite_note-13">[10]</a> with a Spanning Tree BPDU

</caption>

<th style="min-width:42px; border-bottom:none; border-right:none;">Offset

</th>

<th style="border-left:none;"><a href="Octet_(computing)" title="Octet (computing)">Octet</a>

</th>

<th colspan="8">0

</th>

<th colspan="8">1

</th>

<th colspan="8">2

</th>

<th colspan="8">3

</th></tr>

<tr>

<th style="min-width: 42px;border-top: none;">Octet

</th>

</th>

<th style="min-width:11px;">0

</th>

<th style="min-width:11px;">1

</th>

<th style="min-width:11px;">2

</th>

<th style="min-width:11px;">3

</th>

<th style="min-width:11px;">4

</th>

<th style="min-width:11px;">5

</th>

<th style="min-width:11px;">6

</th>

<th style="min-width:11px;">7

</th>

<th style="min-width:11px;">8

</th>

<th style="min-width:11px;">9

</th>

<th style="min-width:16px;">10

</th>

<th style="min-width:16px;">11

</th>

<th style="min-width:16px;">12

</th>

<th style="min-width:16px;">13

</th>

<th style="min-width:16px;">14

</th>

<th style="min-width:16px;">15

</th>

<th style="min-width:16px;">16

</th>

<th style="min-width:16px;">17

</th>

<th style="min-width:16px;">18

</th>

<th style="min-width:16px;">19

</th>

<th style="min-width:16px;">20

</th>

<th style="min-width:16px;">21

</th>

<th style="min-width:16px;">22

</th>

<th style="min-width:16px;">23

</th>

<th style="min-width:16px;">24

</th>

<th style="min-width:16px;">25

</th>

<th style="min-width:16px;">26

</th>

<th style="min-width:16px;">27

</th>

<th style="min-width:16px;">28

</th>

<th style="min-width:16px;">29

</th>

<th style="min-width:16px;">30

</th>

<th style="min-width:16px;">31

</th></tr>

<tr>

<th style="width:35px;">0

</th>

<th style="width:30px;">0

</th>

<td colspan="32" style="border-bottom: none;">Source MAC (5C:A4:7D:1A:52:10)

</td></tr>

<tr>

<th style="width:35px;">4

</th>

<th style="width:30px;">32

</th>

</td>

</td></tr>

<tr>

<th style="width:35px;">8

</th>

<th style="width:30px;">64

</th>

<td colspan="32" style="border-top: none;"><abbr title="Destination MAC (STP multicast address)">Destination MAC</abbr> (01:80:C2:00:00:00)

</td></tr>

<tr>

<th style="width:35px;">12

</th>

<th style="width:30px;">96

</th>

<td colspan="16">Length

</td>

<td colspan="16" style="border-right: none;">Logical Link Control Header↴

</td></tr>

<tr>

<th style="width:35px;">16

</th>

<th style="width:30px;">128

</th>

<td colspan="8" style="border-left: none;">↪LLC (cont.)

</td>

</td></tr>

<tr>

<th style="width:35px;">20

</th>

<th style="width:30px;">160

</th>

<td colspan="32" rowspan="3" style="background: mistyrose;border-top: none;">BPDU payload

</td></tr>

<tr>

<th>24

</th>

<th>192

</th></tr>

<tr>

<th>⋮

</th>

<th>⋮

</th></tr>

<tr>

<th style="width:35px;">⋮

</th>

<th style="width:30px;">⋮

</th>

<td colspan="32">Frame Check Sequence

</td></tr></tbody></table>

<dl><dt>Source MAC: 48 bits</dt>

<dd>A bridge sends a BPDU frame using the unique MAC address of the port itself as a source address. Address 5C:A4:7D:1A:52:10 is an example.</dd>

<dt>Destination MAC: 48 bits</dt>

<dd>The destination MAC address is an STP <a href="Multicast_address" title="Multicast address">multicast address</a>. The <a href="IEEE_802" title="IEEE 802">IEEE 802</a> standard Bridge Group Address is 01:80:C2:00:00:00.<a href="#cite_note-14">[11]</a> However, several proprietary destination MAC addresses for STP exist, like the <a href="#Per-VLAN_Spanning_Tree_and_Per-VLAN_Spanning_Tree_Plus">Cisco proprietary Per-VLAN Spanning Tree</a> address 01:00:0C:CC:CC:CD<a href="#cite_note-15">[12]</a> or the <a href="Extreme_Networks" title="Extreme Networks">Extreme Networks</a> address 03:04:08:00:07:00, and may be used instead of the standard.</dd>

<dt>Length: 16 bits</dt>

<dd>Combined length of the LLC Header, BPDU payload, and FCS.</dd>

<dt>Logical Link Control (LLC): 24 bits</dt>

<dd>Logical Link Control Header.</dd>

<dt>BPDU Payload: Variable</dt>

<dd>The BPDU itself.</dd>

<dt>Frame Check Sequence (FCS): 32 bits</dt>

<dd>Checksum of the frame.</dd></dl>

BPDUs are exchanged regularly (every 2 seconds by default) and enable switches to keep track of network changes and to start and stop forwarding at ports as required. To prevent the delay when connecting hosts to a switch and during some topology changes, <a href="#Rapid_Spanning_Tree_Protocol">Rapid STP</a> was developed, which allows a switch port to rapidly transition into the forwarding state during these situations.

<div class="mw-heading mw-heading3"><h3 id="BPDU_types">BPDU types</h3></div>

There are two types of BPDUs in the original STP specification (802.1D)<a href="#cite_note-802.1D-2004-5">[5]</a>: 63 (the Rapid Spanning Tree (RSTP) extension uses a specific RSTP BPDU).

IEEE 802.1D and <a href="IEEE_802.1aq" title="IEEE 802.1aq">IEEE 802.1aq</a> BPDUs have the following format:

<caption>Topology Change Notificatation BPDU

</caption>

<th style="min-width:42px; border-bottom:none; border-right:none;">Offset

</th>

<th style="border-left:none;"><a href="Octet_(computing)" title="Octet (computing)">Octet</a>

</th>

<th colspan="8">0

</th>

<th colspan="8">1

</th>

<th colspan="8">2

</th>

<th colspan="8">3

</th></tr>

<tr>

<th style="min-width: 42px;border-top: none;">Octet

</th>

</th>

<th style="min-width:11px;">0

</th>

<th style="min-width:11px;">1

</th>

<th style="min-width:11px;">2

</th>

<th style="min-width:11px;">3

</th>

<th style="min-width:11px;">4

</th>

<th style="min-width:11px;">5

</th>

<th style="min-width:11px;">6

</th>

<th style="min-width:11px;">7

</th>

<th style="min-width:11px;">8

</th>

<th style="min-width:11px;">9

</th>

<th style="min-width:16px;">10

</th>

<th style="min-width:16px;">11

</th>

<th style="min-width:16px;">12

</th>

<th style="min-width:16px;">13

</th>

<th style="min-width:16px;">14

</th>

<th style="min-width:16px;">15

</th>

<th style="min-width:16px;">16

</th>

<th style="min-width:16px;">17

</th>

<th style="min-width:16px;">18

</th>

<th style="min-width:16px;">19

</th>

<th style="min-width:16px;">20

</th>

<th style="min-width:16px;">21

</th>

<th style="min-width:16px;">22

</th>

<th style="min-width:16px;">23

</th>

<th style="min-width:16px;">24

</th>

<th style="min-width:16px;">25

</th>

<th style="min-width:16px;">26

</th>

<th style="min-width:16px;">27

</th>

<th style="min-width:16px;">28

</th>

<th style="min-width:16px;">29

</th>

<th style="min-width:16px;">30

</th>

<th style="min-width:16px;">31

</th></tr>

<tr>

<th style="width:35px;">0

</th>

<th style="width:30px;">0

</th>

<td colspan="16">Protocol ID (<style data-mw-deduplicate="TemplateStyles:r886049734">

/* start https://en.wikipedia.org/ */

.mw-parser-output .monospaced{font-family:monospace,monospace}

/* end https://en.wikipedia.org/ */

</style>0x0000)

</td>

<td colspan="8">Version ID (0x00)

</td>

<td colspan="8">BPDU Type (0x80)

</td></tr></tbody></table>

<dl><dt>Protocol ID: 16 bits</dt>

<dd>Protocol ID value. This is set to 0x0000 for all BPDUs.</dd>

<dt>Version ID: 8 bits</dt>

<dd>Version ID. Set to 0x00 for TCN BPDUs.</dd>

<dd>BPDU Type is set to 0x80 for TCN BPDUs.</dd></dl>

Topology change notification (TCN) BPDU, used to announce changes in the network topology, such as port up or port down.

<caption>Configuration BPDU

</caption>

<th style="min-width:42px; border-bottom:none; border-right:none;">Offset

</th>

<th style="border-left:none;"><a href="Octet_(computing)" title="Octet (computing)">Octet</a>

</th>

<th colspan="8">0

</th>

<th colspan="8">1

</th>

<th colspan="8">2

</th>

<th colspan="8">3

</th></tr>

<tr>

<th style="min-width: 42px;border-top: none;">Octet

</th>

</th>

<th style="min-width:11px;">0

</th>

<th style="min-width:11px;">1

</th>

<th style="min-width:11px;">2

</th>

<th style="min-width:11px;">3

</th>

<th style="min-width:11px;">4

</th>

<th style="min-width:11px;">5

</th>

<th style="min-width:11px;">6

</th>

<th style="min-width:11px;">7

</th>

<th style="min-width:11px;">8

</th>

<th style="min-width:11px;">9

</th>

<th style="min-width:16px;">10

</th>

<th style="min-width:16px;">11

</th>

<th style="min-width:16px;">12

</th>

<th style="min-width:16px;">13

</th>

<th style="min-width:16px;">14

</th>

<th style="min-width:16px;">15

</th>

<th style="min-width:16px;">16

</th>

<th style="min-width:16px;">17

</th>

<th style="min-width:16px;">18

</th>

<th style="min-width:16px;">19

</th>

<th style="min-width:16px;">20

</th>

<th style="min-width:16px;">21

</th>

<th style="min-width:16px;">22

</th>

<th style="min-width:16px;">23

</th>

<th style="min-width:16px;">24

</th>

<th style="min-width:16px;">25

</th>

<th style="min-width:16px;">26

</th>

<th style="min-width:16px;">27

</th>

<th style="min-width:16px;">28

</th>

<th style="min-width:16px;">29

</th>

<th style="min-width:16px;">30

</th>

<th style="min-width:16px;">31

</th></tr>

<tr>

<th style="width:35px;">0

</th>

<th style="width:30px;">0

</th>

<td colspan="16">Protocol ID (0x0000)

</td>

<td colspan="8">Version ID

</td>

<td colspan="8">BPDU Type

</td></tr>

<tr>

<th style="width:35px;">4

</th>

<th style="width:30px;">32

</th>

<td colspan="8">Flags

</td>

</td></tr>

<tr>

<th style="width:35px;">8

</th>

<th style="width:30px;">64

</th>

<td colspan="32" style="border-top: none; border-bottom: none;">Root ID

</td></tr>

<tr>

<th style="width:35px;">12

</th>

<th style="width:30px;">96

</th>

</td>

<td colspan="24" style="border-right: none;">Root Path Cost↴

</td></tr>

<tr>

<th style="width:35px;">16

</th>

<th style="width:30px;">128

</th>

<td colspan="8" style="border-left: none;">↪Root Path Cost (cont.)

</td>

</td></tr>

<tr>

<th style="width:35px;">20

</th>

<th style="width:30px;">160

</th>

<td colspan="32" style="border-top: none; border-bottom: none;">Bridge ID

</td></tr>

<tr>

<th style="width:35px;">24

</th>

<th style="width:30px;">192

</th>

</td>

<td colspan="16">Port ID

</td>

<td colspan="8" style="border-right: none;">Message Age↴

</td></tr>

<tr>

<th style="width:35px;">28

</th>

<th style="width:30px;">224

</th>

<td colspan="8" style="border-left: none;">↪Message Age (cont.)

</td>

<td colspan="16">Max Age

</td>

<td colspan="8" style="border-right: none;">Hello Time↴

</td></tr>

<tr>

<th style="width:35px;">32

</th>

<th style="width:30px;">256

</th>

<td colspan="8" style="border-left: none;">↪Hello Time (cont.)

</td>

<td colspan="16">Forward Delay

</td>

<td colspan="8">Version 1 Length

</td></tr>

<tr>

<th style="width:35px;">36

</th>

<th style="width:30px;">288

</th>

<td colspan="16" style="background: linen;">(Version 3 Length)

</td></tr></tbody></table>

<dl><dt>Protocol ID: 16 bits</dt>

<dd>Protocol ID value. This is set to 0x0000 for all BPDUs and represents 802.1D.</dd>

<dt>Version ID: 8 bits</dt>

<dd>Version ID. Set to 0x00 for Config and TCN BPDUs; 0x02 indicates a RST BPDU; 0x03 indicates an MST BPDU; and 0x04 indicates an STP BPDU.</dd>

<dd>BPDU Type is set to 0x80 for TCN BPDUs.</dd>

<dt>Flags: 8 bits</dt>

<dd>Flags.

<dl><dt>Topology Change: 1 bit</dt>

<dd>0 or 1 for Topology Change.</dd>

<dt>Proposal: 1 bit</dt>

<dd>0 (unused) or 1 for Proposal in RST/MST/SPT BPDU.</dd>

<dd>00 (unused) or 01 for Port Role Alternate/Backup in RST/MST/SPT BPDU. 10 for Port Role Root in RST/MST/SPT BPDU. 11 for Port Role Designated in RST/MST/SPT BPD.</dd>

<dt>Learning: 1 bit</dt>

<dd>0 (unused) or 1 for Learning in RST/MST/SPT BPDU.</dd>

<dt>Forwarding: 1 bit</dt>

<dd>0 (unused) or 1 for Forwarding in RST/MST/SPT BPDU.</dd>

<dt>Agreement: 1 bit</dt>

<dd>0 (unused) or 1 for Agreement in RST/MST/SPT BPDU.</dd>

<dd>0 or 1 for Topology Change Acknowledgement.</dd></dl></dd></dl>

<dd>CIST Root ID in MST/SPT BPDU. This field is divided into three parts:

<dl><dt>Priority: 4 bits</dt>

<dd>Root Bridge Priority.</dd>

<dt>System ID Extension: 12 bits</dt>

<dd>Root Bridge System ID Extension.</dd>

<dt>MAC Address: 48 bits</dt>

<dd>Root Bridge MAC Address.</dd></dl></dd></dl>

<dd>CIST External Path Cost in MST/SPT BPDU</dd>

<dt>Bridge ID: 64 bits</dt>

<dd>CIST Regional Root ID in MST/SPT BPDU. This field is divided into three parts:

<dl><dt>Priority: 4 bits</dt>

<dd>Bridge Priority.</dd>

<dt>System ID Extension: 12 bits</dt>

<dd>Bridge System ID Extension.</dd>

<dt>MAC Address: 48 bits</dt>

<dd>Bridge MAC Address.</dd></dl></dd></dl>

<dl><dt>Port ID: 2 bytes</dt>

<dt>Message Age: 2 bytes</dt>

<dt>Max Age: 2 bytes</dt>

<dt>Hello Time: 2 bytes</dt>

<dt>Forward Delay: 2 bytes</dt>

<dt>Version 1 Length: 1 byte</dt>

<dd>0x00 no ver 1 protocol info present. RST, MST, SPT BPDU only.</dd>

<dt>Version 3 Length: 2 bytes</dt>

<dd>Version 3 only; MST, SPT BPDU only.</dd></dl>

Configuration BPDU (CBPDU), used for spanning tree computation and sent by root bridges to provide information to all switches.

<div class="mw-heading mw-heading2"><h2 id="Spanning_Tree_Protocol_standards">Spanning Tree Protocol standards</h2></div>

The first Spanning Tree Protocol was invented in 1985 at the Digital Equipment Corporation by <a href="Radia_Perlman" title="Radia Perlman">Radia Perlman</a>.<a href="#cite_note-perlman_paper-1">[1]</a> In 1990, the IEEE published the first standard for the protocol as 802.1D,<a href="#cite_note-16">[13]</a> based on the algorithm designed by Perlman. Subsequent versions were published in 1998<a href="#cite_note-17">[14]</a> and 2004,<a href="#cite_note-standard-18">[15]</a> incorporating various extensions. The original Perlman-inspired Spanning Tree Protocol, called DEC STP, is not a standard and differs from the IEEE version in message format as well as timer settings. Some bridges implement both the IEEE and the DEC versions of the Spanning Tree Protocol, but their interworking can create issues for the network administrator.<a href="#cite_note-19">[16]</a>

Different implementations of a standard are not guaranteed to <a href="Interoperate" class="mw-redirect" title="Interoperate">interoperate</a>, due for example to differences in default timer settings. The IEEE encourages vendors to provide a <a href="Protocol_Implementation_Conformance_Statement" class="mw-redirect" title="Protocol Implementation Conformance Statement">Protocol Implementation Conformance Statement</a>, declaring which capabilities and options have been implemented,<a href="#cite_note-standard-18">[15]</a> to help users determine whether different implementations will interoperate correctly.

<div class="mw-heading mw-heading3"><h3 id="Rapid_Spanning_Tree_Protocol">Rapid Spanning Tree Protocol</h3></div>

/* start https://en.wikipedia.org/ */

.mw-parser-output .hatnote{font-style:italic}.mw-parser-output div.hatnote{padding-left:1.6em;margin-bottom:0.5em}.mw-parser-output .hatnote i{font-style:normal}.mw-parser-output .hatnote+link+.hatnote{margin-top:-0.5em}@media print{body.ns-0 .mw-parser-output .hatnote{display:none!important}}

/* end https://en.wikipedia.org/ */

</style><div role="note" class="hatnote navigation-not-searchable">Not to be confused with <a href="Real_Time_Streaming_Protocol" class="mw-redirect" title="Real Time Streaming Protocol">Real Time Streaming Protocol</a>.</div>

In 2001, the <a href="IEEE" class="mw-redirect" title="IEEE">IEEE</a> introduced Rapid Spanning Tree Protocol (RSTP) as IEEE 802.1w. RSTP was then incorporated into IEEE 802.1D-2004 making the original STP standard obsolete.<a href="#cite_note-20">[17]</a> RSTP was designed to be backward-compatible with standard STP.

RSTP provides significantly faster spanning tree convergence after a topology change, introducing new convergence behaviors and bridge port roles to accomplish this. While STP can take 30 to 50 seconds to respond to a topology change, RSTP is typically able to respond to changes within 3 × hello times (default: 3 × 2 seconds) or within a few milliseconds of a physical link failure. The hello time is an important and configurable time interval that is used by RSTP for several purposes; its default value is 2 seconds.<a href="#cite_note-21">[18]</a><a href="#cite_note-22">[19]</a>

<div class="mw-heading mw-heading4"><h4 id="Rapid_Spanning_Tree_operation">Rapid Spanning Tree operation</h4></div>

RSTP adds new bridge port roles in order to speed convergence following a link failure:

<ul><li>Root – A forwarding port that is the best port from non-root bridge to root bridge</li>

<li>Designated – A forwarding port for every network segment</li>

<li>Alternate – An alternate path to the root bridge. This path is different from using the root port</li>

<li>Backup – A backup/redundant path to a segment where another bridge port already connects</li>

<li>Disabled – Not strictly part of STP, a network administrator can manually disable a port</li></ul>

The number of switch port states a port can be in has been reduced to three instead of STP's original five:

<ul><li>Discarding – No user data is sent over the port</li>

<li>Learning – The port is not forwarding frames yet, but is populating its MAC address table</li>

<li>Forwarding – The port is fully operational</li></ul>

RSTP operational details:

<ul><li>Detection of root switch failure is done in 3 hello times, which is 6 seconds if the default hello times have not been changed.</li>

<li>Ports may be configured as edge ports if they are attached to a LAN that has no other bridges attached (depending on vendor, admin-edge or portfast mode). These edge ports transition directly to the forwarding state, avoiding problems with hosts expecting an upcoming link to work right away, e.g. with <a href="DHCP" class="mw-redirect" title="DHCP">DHCP</a>. RSTP still continues to monitor the port for BPDUs in case a bridge is connected. RSTP can also be configured to automatically detect edge ports. As soon as the bridge detects a BPDU coming to an edge port, the port becomes a non-edge port.</li>

<li>RSTP calls the connection between two or more switches as a "link-type" connection. A port that operates in full-duplex mode is assumed to be point-to-point link, whereas a half-duplex port (through a hub) is considered a shared port by default. This automatic link type setting can be overridden by explicit configuration. RSTP improves convergence on point-to-point links by reducing the Max-Age time to 3 times Hello interval, removing the STP listening state, and exchanging a handshake between two switches to quickly transition the port to forwarding state. RSTP does not do anything differently from STP on shared links.</li>

<li>Unlike in STP, RSTP will respond to BPDUs sent from the direction of the root bridge. An RSTP bridge will propose its spanning tree information to its designated ports. If another RSTP bridge receives this information and determines this is the superior root information, it sets all its other ports to discarding. The bridge may send an agreement to the first bridge confirming its superior spanning tree information. The first bridge, upon receiving this agreement, knows it can rapidly transition that port to the forwarding state bypassing the listening/learning state transition. This essentially creates a cascading effect away from the root bridge where each designated bridge proposes to its neighbors to determine if it can make a rapid transition. This is one of the major elements that allows RSTP to achieve faster convergence times than STP.</li>

<li>As discussed in the port role details above, RSTP maintains backup details regarding the discarding status of ports. This avoids timeouts if the current forwarding ports were to fail or BPDUs were not received on the root port in a certain interval.</li>

<li>RSTP will revert to legacy STP on an interface if a legacy version of an STP BPDU is detected on that port.</li></ul>

<div class="mw-heading mw-heading2"><h2 id="Standards_for_VLANs">Standards for VLANs</h2></div>

STP and RSTP do not segregate switch ports by VLAN.<a href="#cite_note-Solomon-23">[20]</a> However, in <a href="Ethernet" title="Ethernet">Ethernet</a> switched environments where multiple <a href="VLAN" title="VLAN">VLANs</a> exist, it is often desirable to create multiple spanning trees so that traffic on different VLANs uses different links.

<div class="mw-heading mw-heading3"><h3 id="Proprietary_standards">Proprietary standards</h3></div>

Before the IEEE published a Spanning Tree Protocol standard for VLANs, a number of vendors who sold VLAN-capable switches developed their own Spanning Tree Protocol versions that were VLAN capable. <a href="Cisco" title="Cisco">Cisco</a> developed, implemented and published the Per-VLAN Spanning Tree (PVST) <a href="Proprietary_protocol" title="Proprietary protocol">proprietary protocol</a> using its own proprietary <a href="Cisco_Inter-Switch_Link" title="Cisco Inter-Switch Link">Inter-Switch Link</a> (ISL) for VLAN <a href="Encapsulation_(networking)" title="Encapsulation (networking)">encapsulation</a>, and PVST+ which uses <a href="802.1Q" class="mw-redirect" title="802.1Q">802.1Q</a> VLAN encapsulation. Both standards implement a separate spanning tree for every VLAN. Cisco switches now commonly implement PVST+ and can only implement Spanning Trees for VLANs if the other switches in the LAN implement the same VLAN STP protocol. HP provides PVST and PVST+ compatibility in some of its network switches.<a href="#cite_note-Solomon-23">[20]</a> Some devices from <a href="Force10_Networks" class="mw-redirect" title="Force10 Networks">Force10 Networks</a>, <a href="Alcatel-Lucent" title="Alcatel-Lucent">Alcatel-Lucent</a>, <a href="Extreme_Networks" title="Extreme Networks">Extreme Networks</a>, <a href="Avaya" title="Avaya">Avaya</a>, <a href="Brocade_Communications_Systems" title="Brocade Communications Systems">Brocade Communications Systems</a> and <a href="BLADE_Network_Technologies" class="mw-redirect" title="BLADE Network Technologies">BLADE Network Technologies</a> support PVST+.<a href="#cite_note-24">[21]</a><a href="#cite_note-25">[22]</a><a href="#cite_note-26">[23]</a> Extreme Networks does so with two limitations: Lack of support on ports where the VLAN is untagged/native, and also on the VLAN with ID 1. PVST+ can tunnel across an MSTP Region.<a href="#cite_note-27">[24]</a>

The switch vendor <a href="Juniper_Networks" title="Juniper Networks">Juniper Networks</a> in turn developed and implemented its VLAN Spanning Tree Protocol (VSTP) to provide compatibility with Cisco's PVST, so that the switches from both vendors can be included in one LAN.<a href="#cite_note-Solomon-23">[20]</a> The VSTP protocol is only supported by the EX and MX Series from Juniper Networks. There are two restrictions to the compatibility of VSTP:

<ol><li>VSTP supports only 253 different spanning-tree topologies. If there are more than 253 VLANs, it is recommended to configure RSTP in addition to VSTP, and VLANs beyond 253 will be handled by RSTP.</li>

<li><a href="MVRP" class="mw-redirect" title="MVRP">MVRP</a> does not support VSTP. If this protocol is in use, VLAN membership for trunk interfaces must be statically configured.<a href="#cite_note-28">[25]</a></li></ol>

By default, VSTP uses the RSTP protocol as its core spanning-tree protocol, but usage of STP can be forced if the network includes old bridges.<a href="#cite_note-29">[26]</a> More information about configuring VSTP on Juniper Networks switches was published in the official documentation.<a href="#cite_note-30">[27]</a>

Cisco also published a proprietary version of Rapid Spanning Tree Protocol. It creates a spanning tree for each VLAN, just like PVST. Cisco refers to this as Rapid Per-VLAN Spanning Tree (RPVST).

<div class="mw-heading mw-heading3"><h3 id="Multiple_Spanning_Tree_Protocol">Multiple Spanning Tree Protocol</h3></div>

<div role="note" class="hatnote navigation-not-searchable">Main article: <a href="Multiple_Spanning_Tree_Protocol" title="Multiple Spanning Tree Protocol">Multiple Spanning Tree Protocol</a></div>

The Multiple Spanning Tree Protocol (MSTP), originally defined in <a href="IEEE_802.1s" class="mw-redirect" title="IEEE 802.1s">IEEE 802.1s</a>-2002 and later merged into <a href="IEEE_802.1Q" title="IEEE 802.1Q">IEEE 802.1Q</a>-2005, defines an extension to RSTP to further develop the usefulness of VLANs.

In the standard, a spanning tree that maps one or more VLANs is called a multiple spanning tree (MST). Under MSTP, a spanning tree can be defined for individual VLANs or for groups of VLANs. Furthermore, the administrator can define alternate paths within a spanning tree. Switches are first assigned to an MST region, then VLANs are mapped against or assigned to this MST. A common spanning tree (CST) is an MST to which several VLANs are mapped, this group of VLANs is called MST instance (MSTI). CSTs are backward compatible with the STP and RSTP standard. A MST that has only one VLAN assigned to it is an internal spanning tree (IST).<a href="#cite_note-Solomon-23">[20]</a>

Unlike some proprietary per-VLAN spanning tree implementations,<a href="#cite_note-31">[28]</a> MSTP includes all of its spanning tree information in a single BPDU format. Not only does this reduce the number of BPDUs required to communicate spanning tree information for each VLAN, but it also ensures backward compatibility with RSTP and, in effect, classic STP too. MSTP does this by encoding an additional region of information after the standard RSTP BPDU as well as a number of MSTI messages (from 0 to 64 instances, although in practice many bridges support fewer). Each of these MSTI configuration messages conveys the spanning tree information for each instance. Each instance can be assigned a number of configured VLANs and frames assigned to these VLANs operate in this spanning tree instance whenever they are inside the MST region. In order to avoid conveying their entire VLAN to spanning tree mapping in each BPDU, bridges encode an MD5 digest of their VLAN to instance table in the MSTP BPDU. This digest is then used by other MSTP bridges, along with other administratively configured values, to determine if the neighboring bridge is in the same MST region as itself.

MSTP is fully compatible with RSTP bridges in that an MSTP BPDU can be interpreted by an RSTP bridge as an RSTP BPDU. This not only allows compatibility with RSTP bridges without configuration changes but also causes any RSTP bridges outside of an MSTP region to see the region as a single RSTP bridge regardless of the number of MSTP bridges inside the region itself. In order to further facilitate this view of an MSTP region as a single RSTP bridge, the MSTP protocol uses a variable known as remaining hops as a time to live counter instead of the message age timer used by RSTP. The message age time is only incremented once when spanning-tree information enters an MST region, and therefore RSTP bridges will see a region as only one hop in the spanning tree. Ports at the edge of an MSTP region connected to either an RSTP or STP bridge or an endpoint are known as boundary ports. As in RSTP, these ports can be configured as edge ports to facilitate rapid changes to the forwarding state when connected to endpoints.

<div class="mw-heading mw-heading2"><h2 id="Shortest_path_bridging">Shortest path bridging</h2></div>

<div role="note" class="hatnote navigation-not-searchable">Main article: <a href="IEEE_802.1aq" title="IEEE 802.1aq">IEEE 802.1aq</a></div>

IEEE 802.1aq, also known as Shortest Path Bridging (SPB), allows redundant links between switches to be active through multiple equal cost paths, and provides much larger layer-2 topologies, faster convergence, and improves the use of the mesh topologies through increased bandwidth between all devices by allowing traffic to load share across all paths on a mesh network.<a href="#cite_note-32">[29]</a><a href="#cite_note-33">[30]</a> SPB consolidates multiple existing functionalities, including Spanning Tree Protocol (STP), Multiple Spanning Tree Protocol (MSTP), Rapid Spanning Tree Protocol (RSTP), Link aggregation, and <a href="Multiple_MAC_Registration_Protocol" class="mw-redirect" title="Multiple MAC Registration Protocol">Multiple MAC Registration Protocol</a> (MMRP) into a one link state protocol.<a href="#cite_note-IEEE-34">[31]</a>

<div class="mw-heading mw-heading3"><h3 id="System_ID_Extension">System ID Extension</h3></div>

The bridge ID (BID) is a field inside a BPDU packet. It is eight bytes in length. The first two bytes are the bridge priority, an unsigned integer of 0–65,535. The last six bytes are a <a href="MAC_address" title="MAC address">MAC address</a> supplied by the bridge. Prior to IEEE 802.1D-2004, the first two bytes gave a 16-bit bridge priority. Since IEEE 802.1D-2004, the first four bits are a configurable priority, and the last twelve bits carry the bridge system ID extension. In the case of MST, the bridge system ID extension carries the MSTP instance number. Some vendors set the bridge system ID extension to carry a VLAN ID allowing a different spanning tree per VLAN, such as Cisco's <a href="PVST" class="mw-redirect" title="PVST">PVST</a>.

<div class="mw-heading mw-heading2"><h2 id="Disadvantages_and_current_practice">Disadvantages and current practice</h2></div>

Spanning tree is an older protocol with a longer convergence time. Improper use or implementation can contribute to network disruptions. Blocking links is a crude approach to high availability and preventing loops. Modern networks can make use of all connected links by use of protocols that inhibit, control or suppress the natural behavior of logical or physical topology loops.

Newer, more robust protocols include the <a href="TRILL" title="TRILL">TRILL</a> (Transparent Interconnection of Lots of Links) protocol, also created by Perlman,<a href="#cite_note-35">[32]</a> and <a href="Shortest_Path_Bridging" class="mw-redirect" title="Shortest Path Bridging">Shortest Path Bridging</a> from the IEEE.

Configuring connections between network equipment as <a href="Layer-3" class="mw-redirect" title="Layer-3">layer-3</a> IP links and relying on <a href="IP_routing" title="IP routing">IP routing</a> for resiliency and to prevent loops is a popular alternative.

Switch virtualization techniques like Cisco Virtual Switching System and <a href="Virtual_PortChannel" class="mw-redirect" title="Virtual PortChannel">Virtual PortChannel</a> and HP <a href="Intelligent_Resilient_Framework" title="Intelligent Resilient Framework">Intelligent Resilient Framework</a> combine multiple switches into a single logical entity. Such a <a href="Multi-chassis_link_aggregation_group" title="Multi-chassis link aggregation group">multi-chassis link aggregation group</a> works like a normal <a href="Port_trunk" class="mw-redirect" title="Port trunk">port trunk</a>, only distributed through multiple switches. Conversely, partitioning technologies compartmentalize a single physical chassis into multiple logical entities.

On the edge of the network, loop-detection is configured to prevent accidental loops by users.

<ul><li><a href="Distributed_minimum_spanning_tree" title="Distributed minimum spanning tree">Distributed minimum spanning tree</a></li>

<li><a href="EtherChannel" title="EtherChannel">EtherChannel</a></li>

<li><a href="Ethernet_Automatic_Protection_Switching" title="Ethernet Automatic Protection Switching">Ethernet Automatic Protection Switching</a></li>

<li><a href="Ethernet_Ring_Protection_Switching" title="Ethernet Ring Protection Switching">Ethernet Ring Protection Switching</a></li>

<li><a href="Flex_links" title="Flex links">Flex links</a></li>

<li><a href="Flooding_(computer_networking)" title="Flooding (computer networking)">Flooding (computer networking)</a></li>

<li><a href="Media_Redundancy_Protocol" title="Media Redundancy Protocol">Media Redundancy Protocol</a></li>

<li><a href="Minimum_spanning_tree" title="Minimum spanning tree">Minimum spanning tree</a></li>

<li><a href="Resilient_Ethernet_Protocol" title="Resilient Ethernet Protocol">Resilient Ethernet Protocol</a></li>

<li><a href="Unidirectional_Link_Detection" title="Unidirectional Link Detection">Unidirectional Link Detection</a></li></ul>

<div class="mw-heading mw-heading2"><h2 id="Notes">Notes</h2></div>

/* start https://en.wikipedia.org/ */

.mw-parser-output .reflist{margin-bottom:0.5em;list-style-type:decimal}@media screen{.mw-parser-output .reflist{font-size:90%}}.mw-parser-output .reflist .references{font-size:100%;margin-bottom:0;list-style-type:inherit}.mw-parser-output .reflist-columns-2{column-width:30em}.mw-parser-output .reflist-columns-3{column-width:25em}.mw-parser-output .reflist-columns{margin-top:0.3em}.mw-parser-output .reflist-columns ol{margin-top:0}.mw-parser-output .reflist-columns li{page-break-inside:avoid;break-inside:avoid-column}.mw-parser-output .reflist-upper-alpha{list-style-type:upper-alpha}.mw-parser-output .reflist-upper-roman{list-style-type:upper-roman}.mw-parser-output .reflist-lower-alpha{list-style-type:lower-alpha}.mw-parser-output .reflist-lower-greek{list-style-type:lower-greek}.mw-parser-output .reflist-lower-roman{list-style-type:lower-roman}

/* end https://en.wikipedia.org/ */

</style><div class="reflist reflist-lower-alpha">

<li id="cite_note-7"><a href="#cite_ref-7">^</a> Spanning tree incorporated 802.1t, and per 802.1t, uses the 4 most-significant bits of the 802.1d two-octet priority field as priority, and the least-significant 12 bits of that field as the extended system ID.

</li>

<li id="cite_note-8"><a href="#cite_ref-8">^</a> The original 802.1d envisioned the possibility of the root bridge having more than one port on the same <a href="Network_segment" title="Network segment">network segment</a>, and in that case, the port with the lowest port ID would become the designated port for that network segment, and put into forwarding mode, while its other ports on that same network segment became non-designated ports put into blocking mode. Not all bridge manufacturers follow that rule, some making all ports designated ports and putting them all into forwarding mode.

</li>

<li id="cite_note-10"><a href="#cite_ref-10">^</a> Alternatively the network administrator can configure the switch as a spanning tree root primary or secondary. When configuring the root primary and root secondary the switch will automatically change the priority accordingly, 24,576 and 28,672 respectively with the default configuration.<a href="#cite_note-9">[7]</a>

</li>

</ol></div></div>

<div class="mw-heading mw-heading2"><h2 id="References">References</h2></div>

/* start https://en.wikipedia.org/ */

.mw-parser-output cite.citation{font-style:inherit;word-wrap:break-word}.mw-parser-output .citation q{quotes:"\"""\"""'""'"}.mw-parser-output .citation:target{background-color:rgba(0,127,255,0.133)}.mw-parser-output .id-lock-free.id-lock-free a{background:url("./mw/Lock-green.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-limited.id-lock-limited a,.mw-parser-output .id-lock-registration.id-lock-registration a{background:url("./mw/Lock-gray-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-subscription.id-lock-subscription a{background:url("./mw/Lock-red-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .cs1-ws-icon a{background:url("./mw/Wikisource-logo.svg")right 0.1em center/12px no-repeat}body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-free a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-limited a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-registration a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-subscription a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .cs1-ws-icon a{background-size:contain;padding:0 1em 0 0}.mw-parser-output .cs1-code{color:inherit;background:inherit;border:none;padding:inherit}.mw-parser-output .cs1-hidden-error{display:none;color:var(--color-error,#d33)}.mw-parser-output .cs1-visible-error{color:var(--color-error,#d33)}.mw-parser-output .cs1-maint{display:none;color:#085;margin-left:0.3em}.mw-parser-output .cs1-kern-left{padding-left:0.2em}.mw-parser-output .cs1-kern-right{padding-right:0.2em}.mw-parser-output .citation .mw-selflink{font-weight:inherit}@media screen{.mw-parser-output .cs1-format{font-size:95%}html.skin-theme-clientpref-night .mw-parser-output .cs1-maint{color:#18911f}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .cs1-maint{color:#18911f}}

/* end https://en.wikipedia.org/ */

</style><cite id="CITEREFPerlman1985" class="citation journal cs1"><a href="Radia_Perlman" title="Radia Perlman">Perlman, Radia</a> (1985). <a rel="nofollow" class="external text" href="https://semanticscholar.org/paper/933d8fc9b5ddc0e5e12116c1eb309ab535e6ae75">"An Algorithm for Distributed Computation of a Spanning Tree in an Extended LAN"</a>. ACM SIGCOMM Computer Communication Review. 15 (4): 44–53. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1145%2F318951.319004">10.1145/318951.319004</a>. <a href="S2CID_(identifier)" class="mw-redirect" title="S2CID (identifier)">S2CID</a> <a rel="nofollow" class="external text" href="https://api.semanticscholar.org/CorpusID:61172150">61172150</a>.</cite>

</li>

<cite id="CITEREFPerlman2000" class="citation book cs1"><a href="Radia_Perlman" title="Radia Perlman">Perlman, Radia</a> (2000). Interconnections, Second Edition. USA: Addison-Wesley. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>0-201-63448-1</bdi>.</cite>

</li>

<li id="cite_note-802.1Q-3">^ <a href="#cite_ref-802.1Q_3-0">a</a> <a href="#cite_ref-802.1Q_3-1">b</a> <a rel="nofollow" class="external text" href="http://www.ieee802.org/1/pages/802.1Q-2014.html">Bridges and Bridged Networks</a>

</li>

<li id="cite_note-Angelescu-4">^ <a href="#cite_ref-Angelescu_4-0">a</a> <a href="#cite_ref-Angelescu_4-1">b</a> <a href="#cite_ref-Angelescu_4-2">c</a> <a href="#cite_ref-Angelescu_4-3">d</a> <a href="#cite_ref-Angelescu_4-4">e</a> <a href="#cite_ref-Angelescu_4-5">f</a> <a href="#cite_ref-Angelescu_4-6">g</a> <cite id="CITEREFSilviu_Angelescu2010" class="citation book cs1">Silviu Angelescu (2010). CCNA Certification All-In-One For Dummies. John Wiley & Sons. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>9780470635926</bdi>.</cite>

</li>

<li id="cite_note-802.1D-2004-5">^ <a href="#cite_ref-802.1D-2004_5-0">a</a> <a href="#cite_ref-802.1D-2004_5-1">b</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://web.archive.org/web/20051210051119/http://standards.ieee.org/getieee802/download/802.1D-2004.pdf">"802.1D IEEE Standard for Local and Metropolitan Area Networks. Media Access Control (MAC) Bridges"</a> (PDF). <a href="IEEE" class="mw-redirect" title="IEEE">IEEE</a>. 2004. Archived from <a rel="nofollow" class="external text" href="http://standards.ieee.org/getieee802/download/802.1D-2004.pdf">the original</a> (PDF) on December 10, 2005. Retrieved 19 April 2012.</cite>

</li>

<li id="cite_note-CCNPCSG-6">^ <a href="#cite_ref-CCNPCSG_6-0">a</a> <a href="#cite_ref-CCNPCSG_6-1">b</a> <a href="#cite_ref-CCNPCSG_6-2">c</a> <a href="#cite_ref-CCNPCSG_6-3">d</a> <cite id="CITEREFWade_Edwards,_Terry_Jack,_Todd_Lammle,_Toby_Skandier,_Robert_Padjen,_Arthur_Pfund_&_Carl_Timm2006" class="citation book cs1">Wade Edwards, Terry Jack, Todd Lammle, Toby Skandier, Robert Padjen, Arthur Pfund & Carl Timm (2006). CCNP Complete Study Guide: Exams 642-801, 642-811, 642-821, 642-831. John Wiley & Sons. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>9780782150667</bdi>.</cite><code class="cs1-code">{{cite book}}</code>: CS1 maint: multiple names: authors list (link)

</li>

<li id="cite_note-9"><a href="#cite_ref-9">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.cisco.com/c/m/en_us/techdoc/dc/reference/cli/nxos/commands/l2/spanning-tree-vlan.html">"spanning-tree vlan"</a>. <a href="Cisco_Systems" class="mw-redirect" title="Cisco Systems">Cisco Systems</a>. Retrieved 2020-05-04.</cite>

</li>

<li id="cite_note-11"><a href="#cite_ref-11">^</a> 802.1d-1998 section 8.3.1: The designated port for each LAN is the bridge port for which the value of the root path cost is the lowest: if two or more ports have the same value of root path cost, then first the bridge identifier of their bridges, and their port identifiers are used as tie breakers.

</li>

<li id="cite_note-12"><a href="#cite_ref-12">^</a> 802.1d-1998 section 8.3.2 b) A Bridge that receives a Configuration BPDU on what it decides is its Root Port conveying better information (i.e. highest priority Root Identifier, lowest Root Path Cost, highest priority transmitting Bridge and Port), passes that information on to all the LANs for which it believes itself to be the Designated Bridge.

</li>

<li id="cite_note-13"><a href="#cite_ref-13">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.firewall.cx/networking/ethernet/ieee-8023-frame.html">"The IEEE 802.3 Frame Format"</a>. firewall.cx. Retrieved 31 October 2024.</cite>

</li>

<li id="cite_note-14"><a href="#cite_ref-14">^</a> <cite id="CITEREFFinn" class="citation web cs1">Finn, Norman. <a rel="nofollow" class="external text" href="http://www.ieee802.org/1/files/public/docs2003/provider-bridge-l2-protocols-2.pdf">"Provider Bridge Layer 2 Protocols"</a> (PDF). IEEE 802 LAN/MAN Standards Committee. Retrieved 20 October 2017.</cite>

</li>

<li id="cite_note-15"><a href="#cite_ref-15">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.cisco.com/c/en/us/support/docs/lan-switching/spanning-tree-protocol/24062-146.html#anc5">"Understanding Rapid Spanning Tree Protocol (802.1w)"</a>. Cisco Systems. 1 August 2017. Retrieved 20 March 2020.</cite>

</li>

<li id="cite_note-16"><a href="#cite_ref-16">^</a> <cite id="CITEREFLAN/MAN_Standards_Committee_of_the_IEEE_Computer_Society1990" class="citation book cs1">LAN/MAN Standards Committee of the IEEE Computer Society, ed. (1990). ANSI/IEEE Std 802.1D. IEEE.</cite>

</li>

<li id="cite_note-17"><a href="#cite_ref-17">^</a> <cite id="CITEREFLAN/MAN_Standards_Committee_of_the_IEEE_Computer_Society1998" class="citation book cs1">LAN/MAN Standards Committee of the IEEE Computer Society, ed. (1998). ANSI/IEEE Std 802.1D, 1998 Edition, Part 3: Media Access Control (MAC) Bridges. IEEE.</cite>

</li>

<li id="cite_note-standard-18">^ <a href="#cite_ref-standard_18-0">a</a> <a href="#cite_ref-standard_18-1">b</a> <cite id="CITEREFLAN/MAN_Standards_Committee_of_the_IEEE_Computer_Society2004" class="citation book cs1">LAN/MAN Standards Committee of the IEEE Computer Society, ed. (2004). ANSI/IEEE Std 802.1D – 2004: IEEE Standard for Local and Metropolitan Area Networks: Media Access Control (MAC) Bridges. IEEE.</cite>

</li>

<li id="cite_note-19"><a href="#cite_ref-19">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.cisco.com/c/en/us/support/docs/lan-switching/spanning-tree-protocol/11072-inter-vlan-11072.pdf">"Understanding Issues Related to Inter-VLAN Bridging"</a> (PDF). Cisco Systems, Inc. 11072. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20171014034717/https://www.cisco.com/c/en/us/support/docs/lan-switching/spanning-tree-protocol/11072-inter-vlan-11072.pdf">Archived</a> (PDF) from the original on 2017-10-14.</cite>

</li>

<li id="cite_note-20"><a href="#cite_ref-20">^</a> <cite class="citation cs2">IEEE 802.1D-2004, <a href="IEEE" class="mw-redirect" title="IEEE">IEEE</a>, 2004-06-04, <q>Since the original Spanning Tree Protocol (STP) has been removed from the 2004 revision of IEEE Std 802.1D, an implementation of RSTP is required for any claim of conformance for an implementation of IEEE Std 802.1Q-2003 that refers to the current revision of IEEE Std 802.1D</q></cite>

</li>

<li id="cite_note-21"><a href="#cite_ref-21">^</a> <cite id="CITEREFWaldemar_Wojdak2003" class="citation web cs1 cs1-prop-unfit">Waldemar Wojdak (March 2003). <a rel="nofollow" class="external text" href="https://web.archive.org/web/20060127092023/http://www.compactpci-systems.com/articles/id/?203">"Rapid Spanning Tree Protocol: A new solution from an old technology"</a>. CompactPCI Systems. Archived from the original on January 27, 2006. Retrieved 2008-08-04.</cite>

</li>

<li id="cite_note-22"><a href="#cite_ref-22">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="http://www.cisco.com/en/US/tech/tk389/tk621/technologies_white_paper09186a0080094cfa.shtml">"Understanding Rapid Spanning Tree Protocol (802.1w)"</a>. Retrieved 2008-11-27.</cite>

</li>

<li id="cite_note-Solomon-23">^ <a href="#cite_ref-Solomon_23-0">a</a> <a href="#cite_ref-Solomon_23-1">b</a> <a href="#cite_ref-Solomon_23-2">c</a> <a href="#cite_ref-Solomon_23-3">d</a> <cite id="CITEREFMichael_G._Solomon,_David_Kim_&_Jeffrey_L._Carrell2014" class="citation book cs1">Michael G. Solomon, David Kim & Jeffrey L. Carrell (2014). Fundamentals of Communications and Networking. Jones & Bartlett Publishers. p. 204. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>9781284060157</bdi>.</cite>

</li>

<li id="cite_note-24"><a href="#cite_ref-24">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.force10networks.com/CSPortal20/TechTips/0050B_HowDoIConfigureSpanningTree.aspx">"Technical Documentation"</a>. <a href="Force10" title="Force10">Force10</a>. Retrieved 2011-01-25.</cite>

</li>

<li id="cite_note-25"><a href="#cite_ref-25">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="http://www.extremenetworks.com/libraries/products/DSExtXOS_1030.pdf">"ExtremeXOS Operating System, Version 12.5"</a> (PDF). <a href="Extreme_Networks" title="Extreme Networks">Extreme Networks</a>. 2010. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20061126120914/http://www.extremenetworks.com/libraries/products/DSExtXOS_1030.pdf">Archived</a> (PDF) from the original on 2006-11-26. Retrieved 2011-01-25.</cite>

</li>

<li id="cite_note-26"><a href="#cite_ref-26">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="http://www.bladenetwork.net/userfiles/file/PDFs/WP_PVST_SpanningTree_Cisco.pdf">"BLADE PVST+ Interoperability with Cisco"</a> (PDF). 2006. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20100612021303/http://bladenetwork.net/userfiles/file/PDFs/WP_PVST_SpanningTree_Cisco.pdf">Archived</a> (PDF) from the original on 2010-06-12. Retrieved 2011-01-25.</cite>

</li>

<li id="cite_note-27"><a href="#cite_ref-27">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="http://www.cisco.com/en/US/docs/ios/12_1t/12_1t3/feature/guide/dtbridge.html#wp1020686">"Bridging Between IEEE 802.1Q VLANs"</a>. Cisco Systems. Retrieved 2011-01-25.</cite>

</li>

<li id="cite_note-28"><a href="#cite_ref-28">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://web.archive.org/web/20120407024355/http://www.juniper.net/techpubs/en_US/junos10.0/topics/concept/bridging-mvrp-ex-series.html">"Juniper Networks :: Technical Documentation :: Understanding Multiple VLAN Registration Protocol (MVRP) on EX Series Switches"</a>. www.juniper.net. Archived from <a rel="nofollow" class="external text" href="http://www.juniper.net/techpubs/en_US/junos10.0/topics/concept/bridging-mvrp-ex-series.html">the original</a> on 2012-04-07.</cite>

</li>

<li id="cite_note-29"><a href="#cite_ref-29">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.juniper.net/techpubs/en_US/junos9.4/topics/concept/spanning-trees-ex-series-vstp-understanding.html">"Juniper Networks :: Technical Documentation :: Understanding VSTP for EX-series Switches"</a>.</cite>

</li>

<li id="cite_note-30"><a href="#cite_ref-30">^</a> <a rel="nofollow" class="external text" href="https://www.juniper.net/techpubs/en_US/junos14.1/topics/concept/spanning-trees-ex-series-vstp-understanding.html">Understanding VSTP</a>

</li>

<li id="cite_note-31"><a href="#cite_ref-31">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.cisco.com/en/US/prod/collateral/netmgtsw/ps6504/ps6528/ps2425/white_paper_c07-552114.html#wp9003215">"CiscoWorks LAN Management Solution 3.2 Deployment Guide"</a>. August 2009. Retrieved 2010-01-25.</cite>

</li>

<li id="cite_note-32"><a href="#cite_ref-32">^</a> <cite id="CITEREFPeter_Ashwood-Smith2011" class="citation web cs1">Peter Ashwood-Smith (24 Feb 2011). <a rel="nofollow" class="external text" href="https://web.archive.org/web/20130515115628/http://meetings.apnic.net/__data/assets/pdf_file/0012/32007/APRICOT_SPB_Overview.pdf">"Shortest Path Bridging IEEE 802.1aq Overview"</a> (PDF). Huawei. Archived from <a rel="nofollow" class="external text" href="http://meetings.apnic.net/__data/assets/pdf_file/0012/32007/APRICOT_SPB_Overview.pdf">the original</a> (PDF) on 15 May 2013. Retrieved 11 May 2012.</cite>

</li>

<cite id="CITEREFJim_Duffy2012" class="citation web cs1">Jim Duffy (11 May 2012). <a rel="nofollow" class="external text" href="http://www.pcadvisor.co.uk/news/internet/3357242/largest-illinois-healthcare-system-uproots-cisco-build-40m-private-cloud/">"Largest Illinois healthcare system uproots Cisco to build $40M private cloud"</a>. PC Advisor. Retrieved 11 May 2012. <q>Shortest Path Bridging will replace Spanning Tree in the Ethernet fabric.</q></cite>

</li>

<cite class="citation news cs1"><a rel="nofollow" class="external text" href="http://www.techpowerup.com/165594/IEEE-Approves-New-IEEE-802.1aq-Shortest-Path-Bridging-Standard.html">"IEEE Approves New IEEE 802.1aq Shortest Path Bridging Standard"</a>. Tech Power Up. 7 May 2012. Retrieved 11 May 2012.</cite>

</li>

<a rel="nofollow" class="external text" href="https://www.captechu.edu/blog/dr-radia-perlman-one-of-first-female-programmers-and-inventor-internets-protocols">"Dr. Radia Perlman: One of the First Female Programmers and Inventor the Internet's Protocols"</a>.

</li>

</ol></div></div>

<div class="mw-heading mw-heading2"><h2 id="External_links">External links</h2></div>

/* start https://en.wikipedia.org/ */

.mw-parser-output .side-box{margin:4px 0;box-sizing:border-box;border:1px solid #aaa;font-size:88%;line-height:1.25em;background-color:var(--background-color-interactive-subtle,#f8f9fa);display:flow-root}.mw-parser-output .infobox .side-box{font-size:100%}.mw-parser-output .side-box-abovebelow,.mw-parser-output .side-box-text{padding:0.25em 0.9em}.mw-parser-output .side-box-image{padding:2px 0 2px 0.9em;text-align:center}.mw-parser-output .side-box-imageright{padding:2px 0.9em 2px 0;text-align:center}@media(min-width:500px){.mw-parser-output .side-box-flex{display:flex;align-items:center}.mw-parser-output .side-box-text{flex:1;min-width:0}}@media(min-width:720px){.mw-parser-output .side-box{width:238px}.mw-parser-output .side-box-right{clear:right;float:right;margin-left:1em}.mw-parser-output .side-box-left{margin-right:1em}}

/* end https://en.wikipedia.org/ */

</style><style data-mw-deduplicate="TemplateStyles:r1237033735">

/* start https://en.wikipedia.org/ */

@media print{body.ns-0 .mw-parser-output .sistersitebox{display:none!important}}@media screen{html.skin-theme-clientpref-night .mw-parser-output .sistersitebox img[src*="Wiktionary-logo-en-v2.svg"]{background-color:white}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .sistersitebox img[src*="Wiktionary-logo-en-v2.svg"]{background-color:white}}

/* end https://en.wikipedia.org/ */

</style><div class="side-box side-box-right sistersitebox"><style data-mw-deduplicate="TemplateStyles:r1126788409">

/* start https://en.wikipedia.org/ */

.mw-parser-output .plainlist ol,.mw-parser-output .plainlist ul{line-height:inherit;list-style:none;margin:0;padding:0}.mw-parser-output .plainlist ol li,.mw-parser-output .plainlist ul li{margin-bottom:0}

/* end https://en.wikipedia.org/ */

</style>

<div class="side-box-text plainlist">Wikimedia Commons has media related to <a href="https://commons.wikimedia.org/wiki/Category:Spanning_tree_protocol" class="extiw external" title="commons:Category:Spanning tree protocol">Spanning Tree Protocol</a>.</div></div>

</div>

<ul><li><a rel="nofollow" class="external text" href="http://www.cisco.com/en/US/tech/tk389/tk621/tsd_technology_support_protocol_home.html">Cisco home page for the Spanning-Tree protocol family</a> (discusses CST, MISTP, PVST, PVST+, RSTP, STP)</li>

<li><a rel="nofollow" class="external text" href="https://wiki.wireshark.org/STP">STP article in the Wireshark wiki</a> Includes a sample PCAP-file of captured STP traffic.</li>

<li><cite id="CITEREFPerlman" class="citation web cs1"><a href="Radia_Perlman" title="Radia Perlman">Perlman, Radia</a>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20110719212324/http://www.csua.berkeley.edu/~ranga/humor/algorhyme.txt">"Algorhyme"</a>. <a href="University_of_California_at_Berkeley" class="mw-redirect" title="University of California at Berkeley">University of California at Berkeley</a>. Archived from <a rel="nofollow" class="external text" href="http://www.csua.berkeley.edu/~ranga/humor/algorhyme.txt">the original</a> on 2011-07-19.</cite></li>

<li>IEEE Standards

<ul><li><a rel="nofollow" class="external text" href="https://web.archive.org/web/20051210051119/http://standards.ieee.org/getieee802/download/802.1D-2004.pdf">ANSI/IEEE 802.1D-2004 standard</a>, section 17 discusses RSTP (Regular STP is no longer a part of this standard. This is pointed out in section 8.)</li>

<li><a rel="nofollow" class="external text" href="https://web.archive.org/web/20070913195704/http://standards.ieee.org/getieee802/download/802.1Q-2005.pdf">ANSI/IEEE 802.1Q-2005 standard</a>, section 13 discusses MSTP</li></ul></li>

<li>RFCs

<ul><li>RFC <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc4363">4363</a>–2006, proposed standard, Definitions of Managed Objects for Bridges with Traffic Classes, Multicast Filtering, and Virtual LAN Extensions</li>

<li>RFC <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc4188">4188</a>–2005, proposed standard, Definitions of Managed Objects for Bridges</li>

<li>RFC <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc2674">2674</a>–1999, proposed standard, Definitions of Managed Objects for Bridges with Traffic Classes, Multicast Filtering and Virtual LAN Extensions</li>

<li>RFC <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc1525">1525</a>–1993 – SBRIDGEMIB, proposed standard, Definitions of Managed Objects for Source Routing Bridges</li>

<li>RFC <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc1493">1493</a>–1993 – BRIDGEMIB, draft standard, Definitions of Managed Objects for Bridges</li></ul></li>

<li><a rel="nofollow" class="external text" href="https://web.archive.org/web/20110812152242/http://blog.ipexpert.com/2010/03/22/spanning-tree-direct-vs-indirect-link-failures/">Spanning Tree Direct vs Indirect Link Failures – CCIE Study</a></li>

<li><a rel="nofollow" class="external text" href="https://web.archive.org/web/20151227040910/http://www.networkel.com/2015/10/spanning-tree-protocol-stp-no-loop.html">Spanning Tree Protocol Overview</a></li></ul>

/* start https://en.wikipedia.org/ */

.mw-parser-output .navbox{box-sizing:border-box;border:1px solid #a2a9b1;width:100%;clear:both;font-size:88%;text-align:center;padding:1px;margin:1em auto 0}.mw-parser-output .navbox .navbox{margin-top:0}.mw-parser-output .navbox+.navbox,.mw-parser-output .navbox+.navbox-styles+.navbox{margin-top:-1px}.mw-parser-output .navbox-inner,.mw-parser-output .navbox-subgroup{width:100%}.mw-parser-output .navbox-group,.mw-parser-output .navbox-title,.mw-parser-output .navbox-abovebelow{padding:0.25em 1em;line-height:1.5em;text-align:center}.mw-parser-output .navbox-group{white-space:nowrap;text-align:right}.mw-parser-output .navbox,.mw-parser-output .navbox-subgroup{background-color:#fdfdfd}.mw-parser-output .navbox-list{line-height:1.5em;border-color:#fdfdfd}.mw-parser-output .navbox-list-with-group{text-align:left;border-left-width:2px;border-left-style:solid}.mw-parser-output tr+tr>.navbox-abovebelow,.mw-parser-output tr+tr>.navbox-group,.mw-parser-output tr+tr>.navbox-image,.mw-parser-output tr+tr>.navbox-list{border-top:2px solid #fdfdfd}.mw-parser-output .navbox-title{background-color:#ccf}.mw-parser-output .navbox-abovebelow,.mw-parser-output .navbox-group,.mw-parser-output .navbox-subgroup .navbox-title{background-color:#ddf}.mw-parser-output .navbox-subgroup .navbox-group,.mw-parser-output .navbox-subgroup .navbox-abovebelow{background-color:#e6e6ff}.mw-parser-output .navbox-even{background-color:#f7f7f7}.mw-parser-output .navbox-odd{background-color:transparent}.mw-parser-output .navbox .hlist td dl,.mw-parser-output .navbox .hlist td ol,.mw-parser-output .navbox .hlist td ul,.mw-parser-output .navbox td.hlist dl,.mw-parser-output .navbox td.hlist ol,.mw-parser-output .navbox td.hlist ul{padding:0.125em 0}.mw-parser-output .navbox .navbar{display:block;font-size:100%}.mw-parser-output .navbox-title .navbar{float:left;text-align:left;margin-right:0.5em}body.skin--responsive .mw-parser-output .navbox-image img{max-width:none!important}@media print{body.ns-0 .mw-parser-output .navbox{display:none!important}}

/* end https://en.wikipedia.org/ */

</style></div><div role="navigation" class="navbox" aria-labelledby="IEEE_standards209" style="padding:3px"><table class="nowraplinks hlist mw-collapsible autocollapse navbox-inner" style="border-spacing:0;background:transparent;color:inherit"><tbody><tr><th scope="col" class="navbox-title" colspan="2"><div id="IEEE_standards209" style="font-size:114%;margin:0 4em"><a href="IEEE_Standards_Association" title="IEEE Standards Association">IEEE standards</a></div></th></tr><tr><th scope="row" class="navbox-group" style="width:1%">Current</th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="IEEE_754-2008_revision" title="IEEE 754-2008 revision">Revision</a></li></ul></li>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%"><a href="IEEE_802" title="IEEE 802">802 series</a></th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em"></div><table class="nowraplinks navbox-subgroup" style="border-spacing:0"><tbody><tr><th scope="row" class="navbox-group" style="width:1%"><a href="IEEE_802" title="IEEE 802">802</a></th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="WiMAX" title="WiMAX">WiMAX · d · e</a></li></ul></li>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%"><a href="IEEE_802.1" title="IEEE 802.1">802.1</a></th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em">

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%"><a href="IEEE_802.3" title="IEEE 802.3">802.3</a> (<a href="Ethernet" title="Ethernet">Ethernet</a>)</th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em">

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%"><a href="IEEE_802.11" title="IEEE 802.11">802.11</a> (<a href="Wi-Fi" title="Wi-Fi">Wi-Fi</a>)</th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em">

<li><a href="IEEE_802.11_(legacy_mode)" title="IEEE 802.11 (legacy mode)">legacy mode</a></li>

<li><a href="IEEE_802.11ad" title="IEEE 802.11ad">ad</a> (<a href="WiGig" title="WiGig">WiGig</a>)</li>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%"><a href="IEEE_802.15" title="IEEE 802.15">802.15</a></th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="IEEE_802.15.1" class="mw-redirect" title="IEEE 802.15.1">.1</a> (<a href="Bluetooth" title="Bluetooth">Bluetooth</a>)</li>

<li><a href="IEEE_802.15.4" title="IEEE 802.15.4">.4</a> (<a href="Zigbee" title="Zigbee">Zigbee</a>)</li>

</div></td></tr></tbody></table><div></div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Proposed</th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em">

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Superseded</th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em">

</div></td></tr><tr><td class="navbox-abovebelow" colspan="2"><div>

<ul><li> Category</li></ul>

</div></td></tr></tbody></table></div></div><div><div class="zim-footer">

This article is issued from <a class="external text" title="Last edited on 2025-05-30" href="https://en.wikipedia.org/wiki/?title=Spanning_Tree_Protocol&oldid=1293128283">Wikipedia</a>. The text is available under <a class="external text" href="https://creativecommons.org/licenses/by-sa/4.0/deed.en">Creative Commons Attribution-Share Alike 4.0</a> unless otherwise noted. Additional terms may apply for the media files.

</div>

</div></div>

</div>

</main>

</div>

</body></html>